-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(toolchain): bump to 2022-10-16 #5119
Conversation
The ICE is fixed. Now we have TAIT bug 🤪 rust-lang/rust#101750 |
Really want rust-lang/cargo#11114 after bumping. 🤤 |
#![expect(clippy::iter_kv_map, reason = "FIXME: fix later")] | ||
#![expect( | ||
clippy::or_fun_call, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👀
.ok_or(ValueEncodingError::InvalidNaiveTimeEncoding(secs, nano))?, | ||
.ok_or_else(|| ValueEncodingError::InvalidNaiveTimeEncoding(secs, nano))?, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There shouldn't be any difference for enum construction.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build of |
It seems that Rust is very slow with resolving futures_async_stream. It took about 1sec for each resolving. |
To reproduce, |
I'll take a look. |
Unluckily, the bombing obligations seem to originate from StateTableIter
which cases all executors to have a lot of obligations, whereas hash join needs a lot of specialization, and cases the most problems. |
After changing
|
My wild guess is that while rustc allows more lifetime generics in the latest version, some wrongly-labeled lifetimes will cause compile issues. Every time we add |
turn to @wenym1 |
IIRC storage have many unnecessary generics, but I’m not sure whether it’s related. |
I feel this issue more related to StateTable implementation than HummockStorage itself. The obligations will only bomb when processing StateTable-related code. |
Will implementing state table iterator manually with |
I'm not sure, but I'd suggest investigating where's the obligations from. |
Sure. I'll handle it. |
Signed-off-by: Bugen Zhao <i@bugenzhao.com>
#1334 can be closed after this |
I'll take over this PR and get it merged with my pace. |
Thank you guys very much |
close in favor of #6025 |
I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?